-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update rust crate axum to 0.7.0 #66
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/axum-0.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
from
November 29, 2022 10:08
2d6a8a7
to
f172290
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.6.0
fix(deps): update rust crate axum to 0.6.1
Nov 29, 2022
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
4 times, most recently
from
December 13, 2022 08:18
595b19c
to
0290585
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.6.1
Update Rust crate axum to 0.6.1
Dec 17, 2022
renovate
bot
changed the title
Update Rust crate axum to 0.6.1
fix(deps): update rust crate axum to 0.6.1
Dec 17, 2022
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
3 times, most recently
from
January 9, 2023 16:07
ccf70bb
to
017c471
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.6.1
fix(deps): update rust crate axum to 0.6.2
Jan 9, 2023
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
from
January 21, 2023 00:26
017c471
to
8c5cf8c
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.6.2
fix(deps): update rust crate axum to 0.6.3
Jan 21, 2023
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
from
January 24, 2023 13:21
8c5cf8c
to
80c2e08
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.6.3
fix(deps): update rust crate axum to 0.6.4
Jan 24, 2023
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
3 times, most recently
from
February 12, 2023 01:25
7ffc87e
to
eb72909
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.6.4
fix(deps): update rust crate axum to 0.6.5
Feb 12, 2023
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
3 times, most recently
from
February 12, 2023 16:07
ce2eda7
to
174fd30
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.6.5
fix(deps): update rust crate axum to 0.6.6
Feb 12, 2023
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
from
February 17, 2023 14:44
174fd30
to
c11de8a
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.6.6
fix(deps): update rust crate axum to 0.6.7
Feb 17, 2023
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
from
February 24, 2023 14:40
c11de8a
to
c3ea436
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.6.7
fix(deps): update rust crate axum to 0.6.8
Feb 24, 2023
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
2 times, most recently
from
February 25, 2023 13:38
d622bbe
to
0da52e2
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.6.19
fix(deps): update rust crate axum to 0.6.20
Aug 3, 2023
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
2 times, most recently
from
September 6, 2023 20:43
5600802
to
25f2c61
Compare
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
2 times, most recently
from
October 17, 2023 21:50
064e42c
to
f0928dc
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.6.20
fix(deps): update rust crate axum to 0.7.1
Nov 27, 2023
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
from
November 27, 2023 09:20
f0928dc
to
31caeda
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.7.1
fix(deps): update rust crate axum to 0.7.2
Dec 4, 2023
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
from
December 4, 2023 12:20
31caeda
to
4a3ce0e
Compare
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
from
December 29, 2023 19:55
4a3ce0e
to
fa9d805
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.7.2
fix(deps): update rust crate axum to 0.7.3
Dec 29, 2023
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
from
January 13, 2024 16:00
fa9d805
to
5650b85
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.7.3
fix(deps): update rust crate axum to 0.7.4
Jan 13, 2024
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
from
March 24, 2024 20:25
5650b85
to
178ee74
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.7.4
fix(deps): update rust crate axum to 0.7.5
Mar 24, 2024
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
3 times, most recently
from
April 17, 2024 00:21
b0638d3
to
71b9f73
Compare
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
from
May 5, 2024 10:24
71b9f73
to
6dc23d7
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.7.5
fix(deps): update rust crate axum to 0.7.0
May 5, 2024
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
4 times, most recently
from
June 18, 2024 02:57
28814e3
to
c7fdd24
Compare
|
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
3 times, most recently
from
September 27, 2024 03:59
5de319b
to
8a9dba5
Compare
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
from
September 27, 2024 06:05
8a9dba5
to
2bac395
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.5.17
->0.7.0
Release Notes
tokio-rs/axum (axum)
v0.7.7
: axum v0.7.7Compare Source
rustdoc now generates tables of content in the sidebar (#2921)
v0.7.6
: axum - v0.7.6Compare Source
Arc
during deserialization ofPath
axum::serve::Serve::tcp_nodelay
andaxum::serve::WithGracefulShutdown::tcp_nodelay
(#2653)Router::has_routes
function (#2790)Serve::local_addr
andWithGracefulShutdown::local_addr
functions (#2881)v0.7.5
: axum - v0.7.5Compare Source
axum::serve
directly witha
Router
orMethodRouter
(#2586)h2
is no longer pulled as a dependency unless thehttp2
featureis enabled (#2605)
v0.7.4
: axum - v0.7.4Compare Source
debug_handler
on tuple response types (#2201)must_use
attribute toServe
andWithGracefulShutdown
(#2484)axum_core::body::BodyDataStream
from axumv0.7.3
: axum - v0.7.3Compare Source
Body
implementsFrom<()>
now (#2411)tracing
feature by default (#2460)serve
(#2398)RouterIntoService
implementsClone
(#2456)v0.7.2
: axum - v0.7.2Compare Source
axum::body::to_bytes
(#2373)serve
(#2400)v0.7.1
: axum - v0.7.1Compare Source
v0.7.0
: axum - v0.7.0Compare Source
WebSocketUpgrade::max_send_queue
(i.e. the
B
type param has been removed) (#1751 and #1789):FromRequestParts
FromRequest
HandlerService
HandlerWithoutStateExt
Handler
LayeredFuture
Layered
MethodRouter
Next
RequestExt
RouteFuture
Route
Router
hyper::Body
as that type is removedin hyper 1.0. Instead axum has its own body type at
axum::body::Body
(#1751)extract::BodyStream
has been removed asbody::Body
implements
Stream
andFromRequest
directly (#1751)sse::Event::json_data
to useaxum_core::Error
as its error type (#1762)DefaultOnFailedUpdgrade
toDefaultOnFailedUpgrade
(#1664)OnFailedUpdgrade
toOnFailedUpgrade
(#1664)TypedHeader
has been move toaxum-extra
(#1850)Empty
andFull
. Useaxum::body::Body::empty
andaxum::body::Body::from
respectively (#1789)IntoResponse::into_response
must useaxum::body::Body
as the body type.axum::response::Response
does this(#1789)
BoxBody
type alias and itsbox_body
constructor. Use
axum::body::Body::new
instead (#1789)RawBody
extractor.axum::body::Body
implementsFromRequest
directly (#1789)http-body
no longer implementIntoResponse
:Full
, useBody::from
insteadEmpty
, useBody::empty
insteadBoxBody
, useBody::new
insteadUnsyncBoxBody
, useBody::new
insteadMapData
, useBody::new
insteadMapErr
, useBody::new
insteadaxum::extract::Request
type alias where the body isaxum::body::Body
(#1789)Router::as_service
andRouter::into_service
to workaroundtype inference issues when calling
ServiceExt
methods on aRouter
(#1835)axum::Server
as it was removed in hyper 1.0. Insteaduse
axum::serve(listener, service)
or hyper/hyper-util for more configuration options (#1868)Router::nest
.Routers nested with
Router::nest_service
will no longer inherit fallbacks (#1956)Sec-WebSocket-Key
header inWebSocketUpgrade
(#1972)axum::extract::Query::try_from_uri
(#2058)IntoResponse
forBox<str>
andBox<[u8]>
([#2035])MethodFilter
. It no longer uses bitflags (#2073).source()
of composite rejections (#2030)#[debug_handler]
(#2014)IntoResponse
for(R,) where R: IntoResponse
(#2143)NestedPath
extractor (#1924)handle_error
function to existingServiceExt
trait (#2235)impl<T> IntoResponse(Parts) for Extension<T>
now requiresT: Clone
, as that is required by the http crate (#1882)axum::Json::from_bytes
(#2244)FromRequestParts
forhttp::request::Parts
(#2328)FromRequestParts
forhttp::Extensions
(#2328)DefaultBodyLimit
to individual routes (#2157)v0.6.20
: axum - v0.6.20Compare Source
WebSocketUpgrade::write_buffer_size
andWebSocketUpgrade::max_write_buffer_size
WebSocketUpgrade::max_send_queue
Handler
forT: IntoResponse
(#2140)v0.6.19
: axum - v0.6.19Compare Source
axum::extract::Query::try_from_uri
(#2058)IntoResponse
forBox<str>
andBox<[u8]>
(#2035).source()
of composite rejections (#2030)#[debug_handler]
(#2014)v0.6.18
: axum - v0.6.18Compare Source
Sec-WebSocket-Key
header inWebSocketUpgrade
(#1972)v0.6.17
: axum - v0.6.17Compare Source
CONNECT
requests (#1958)v0.6.16
: axum - v0.6.16Compare Source
MatchedPath
in fallbacks (#1934)Router
with something nested at/
was used as a fallback (#1934)Router::new().fallback(...)
isn't optimal (#1940)v0.6.15
: axum - v0.6.15Compare Source
v0.6.14
: axum - v0.6.14Compare Source
v0.6.13
: axum - v0.6.13Compare Source
axum::rejection=trace
target (#1890)Router::nest
introduced in0.6.0.
nest
now flattens the routes which performs better (#1711)MatchedPath
in nested handlers now gives the fullmatched path, including the nested path (#1711)
Deref
andDerefMut
for built-in extractors (#1922)v0.6.12
: axum - v0.6.12Compare Source
IntoResponse
forMultipartError
(#1861)v0.6.11
: axum - v0.6.11Compare Source
S: Debug
forimpl Debug for Router<S>
(#1836)v0.6.10
: axum - v0.6.10Compare Source
#[must_use]
attributes to types that do nothing unless used (#1809)TypedHeader
extractor (#1810)Router
via a dynamic library (#1806)v0.6.9
: axum - v0.6.9Compare Source
v0.6.8
: axum - v0.6.8Compare Source
Allow
missing from routers with middleware (#1773)KeepAlive::event
for customizing the event sent for SSE keep alive (#1729)v0.6.7
: axum - v0.6.7Compare Source
FormRejection::FailedToDeserializeFormBody
which is returnedif the request body couldn't be deserialized into the target type, as opposed
to
FailedToDeserializeForm
which is only for query parameters (#1683)MockConnectInfo
for settingConnectInfo
during tests (#1767)v0.6.6
: axum - v0.6.6Compare Source
MethodRouter
toRouter::fallback
(#1730)v0.6.5
: axum - v0.6.5Compare Source
#[debug_handler]
sometimes giving wrong borrow related suggestions (#1710)impl IntoResponse
as the return type from handler functions (#1736)v0.6.4
: axum - v0.6.4Compare Source
v0.6.3
: axum - v0.6.3Compare Source
IntoResponse
for&'static [u8; N]
and[u8; N]
(#1690)Path
support types usingserde::Deserializer::deserialize_any
(#1693)RawPathParams
(#1713)Clone
andService
foraxum::middleware::Next
(#1712)v0.6.2
: axum - v0.6.2Compare Source
body_text
andstatus
methods to built-in rejections (#1612)runtime
feature ofhyper
when usingtokio
(#1671)v0.6.1
: axum - v0.6.1Compare Source
Router::with_state
(#1580)v0.6.0
: axum - v0.6.0Compare Source
Routing
fixed: Nested routers are now allowed to have fallbacks (#1521):
The outer router's fallback will still apply if a nested router doesn't have
its own fallback:
breaking: The request
/foo/
no longer matches/foo/*rest
. If you wantto match
/foo/
you have to add a route specifically for that (#1086)For example:
breaking: Path params for wildcard routes no longer include the prefix
/
. e.g./foo.js
will match/*filepath
with a value offoo.js
, not/foo.js
(#1086)For example:
fixed: Routes like
/foo
and/*rest
are no longer consideredoverlapping.
/foo
will take priority (#1086)For example:
breaking: Automatic trailing slash redirects have been removed.
Previously if you added a route for
/foo
, axum would redirect calls to/foo/
to/foo
(or vice versa for/foo/
):Either explicitly add routes for
/foo
and/foo/
or useaxum_extra::routing::RouterExt::route_with_tsr
if you want the old behavior(#1119)
breaking:
Router::fallback
now only acceptsHandler
s (similarly towhat
get
,post
, etc. accept). Use the newRouter::fallback_service
forsetting any
Service
as the fallback (#1155)This fallback on 0.5:
Becomes this in 0.6
changed:
Router::nest
now only acceptsRouter
s, the general-purposeService
nesting method has been renamed tonest_service
(#1368)breaking: Allow
Error: Into<Infallible>
forRoute::{layer, route_layer}
(#924)breaking:
MethodRouter
now panics on overlapping routes (#1102)breaking:
Router::route
now only acceptsMethodRouter
s created withget
,post
, etc. Use the newRouter::route_service
for routing toany
Service
s (#1155)breaking: Adding a
.route_layer
onto aRouter
orMethodRouter
without any routes will now result in a panic. Previously, this just did
nothing. #1327
breaking:
RouterService
has been removed sinceRouter
now implementsService
when the state is()
. UseRouter::with_state
to provide thestate and get a
Router<()>
. Note thatRouterService
only existed in thepre-releases, not 0.5 (#1552)
Extractors
added: Added new type safe
State
extractor. This can be used withRouter::with_state
and gives compile errors for missing states, whereasExtension
would result in runtime errors (#1155)We recommend migrating from
Extension
toState
for sharing application state since that is more typesafe and faster. That is done by using
Router::with_state
andState
.This setup in 0.5
Becomes this in 0.6 using
State
:If you have multiple extensions, you can use fields on
AppState
and implementFromRef
:breaking: It is now only possible for one extractor per handler to consume
the request body. In 0.5 doing so would result in runtime errors but in 0.6 it
is a compile error (#1272)
axum enforces this by only allowing the last extractor to consume the
request.
For example:
This is done by reworking the
FromRequest
trait and introducing a newFromRequestParts
trait.If your extractor needs to consume the request body then you should implement
FromRequest
, otherwise implementFromRequestParts
.This extractor in 0.5:
Becomes this in 0.6:
For an example of how to write an extractor that accepts different
Content-Types
see the [parse-body-based-on-content-type
][parse-body-based-on-content-type] example.added:
FromRequest
andFromRequestParts
derive macro re-exports from[
axum-macros
][axum-macros] behind themacros
feature (#1352)added: Add
RequestExt
andRequestPartsExt
which adds conveniencemethods for running extractors to
http::Request
andhttp::request::Parts
(#1301)added:
JsonRejection
now displays the path at which a deserializationerror occurred (#1371)
added: Add
extract::RawForm
for accessing raw urlencoded query bytes or request body (#1487)fixed: Used
400 Bad Request
forFailedToDeserializeQueryString
rejections, instead of
422 Unprocessable Entity
(#1387)changed: The inner error of a
JsonRejection
is nowserde_path_to_error::Error<serde_json::Error>
. Previously it wasserde_json::Error
(#1371)changed: The default body limit now applies to the
Multipart
extractor (#1420)breaking:
ContentLengthLimit
has been removed. UseDefaultBodyLimit
instead (#1400)breaking:
RequestParts
has been removed as part of theFromRequest
rework (#1272)
breaking:
BodyAlreadyExtracted
has been removed (#1272)breaking: The following types or traits have a new
S
type paramwhich represents the state (#1155):
Router
, defaults to()
MethodRouter
, defaults to()
FromRequest
, no defaultHandler
, no defaultbreaking:
MatchedPath
can now no longer be extracted in middleware fornested routes. In previous versions it returned invalid data when extracted
from a middleware applied to a nested router.
MatchedPath
can still beextracted from handlers and middleware that aren't on nested routers (#1462)
breaking: Rename
FormRejection::FailedToDeserializeQueryString
toFormRejection::FailedToDeserializeForm
(#1496)Middleware
middleware::from_fn
functions (#1088)middleware::from_fn_with_state
to enable running extractors that requirestate (#1342)
middleware::from_extractor_with_state
(#1396)map_request
,map_request_with_state
for transforming therequest with an async function (#1408)
map_response
,map_response_with_state
for transforming theresponse with an async function (#1414)
IntoResponse
(#1152)extractor_middleware
which was previously deprecated.Use
axum::middleware::from_extractor
instead (#1077)Handler::layer
to haveInfallible
as the error type (#1152)Misc
simple-router-wasm
examplefor more details (#1382)
ServiceExt
with methods for turning anyService
into aMakeService
similarly toRouter::into_make_service
(#1302)From
impls have been added toextract::ws::Message
to be more inline with
tungstenite
(#1421)#[derive(axum::extract::FromRef)]
(#1430)accept_unmasked_frames
setting in WebSocketUpgrade (#1529)WebSocketUpgrade::on_failed_upgrade
to customize what to dowhen upgrading a connection fails (#1539)
#[track_caller]
so the errormessage points to where the user added the invalid route, rather than
somewhere internally in axum (#1248)
S: Service
, the bounds have beenrelaxed so the response type must implement
IntoResponse
rather than being aliteral
Response
tokio
default feature needed for WASM support. If youdon't need WASM support but have
default_features = false
for other reasonsyou likely need to re-enable the
tokio
feature (#1382)handler::{WithState, IntoService}
are merged into one type,named
HandlerService
(#1418)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.